Information landscape modeling, analysis and validation

ABSTRACT

Managing and validating a project using an information landscape. Embodiments include providing an information landscape including a topology of landscape elements for the project, linking the topology of landscape elements to a plurality of solution artifacts, and validating at least one of the plurality of solution artifacts and semantics of the information landscape.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/447,572, filed Apr. 16, 2012, which is a continuation of U.S. patentapplication Ser. No. 12/825,253, filed Jun. 28, 2010, which is acontinuation of U.S. patent application Ser. No. 15/829,726 filed onDec. 1, 2017. The aforementioned related patent applications are hereinincorporated by reference in its entirety.

BACKGROUND Field

Embodiments of the invention are generally related to informationintegration. And more specifically, embodiments are related totechniques for managing and validating an information landscape.

Description of the Related Art

Information integration projects are typically very complex projectswhich may involve multiple stakeholders, each with different goals andconcerns. Furthermore, each of the stakeholders may view the projectfrom a different perspective. In planning the project, the stakeholdersmay reach a common agreement regarding various solution components ofthe project. Such an agreement may be memorialized in a document.However, any such document must be constantly maintained throughout theproject's lifecycle in order to maintain the document's accuracy.Without this maintenance, the document may quickly become obsolete andcontain various inaccuracies and outdated information. However, suchmaintenance is currently a manual process that requires a significantamount of time and resources and is often a very error-prone process.

SUMMARY

Embodiments of the invention provide a computer-implemented method,computer program product, and system for providing an informationlandscape for a project, wherein the information landscape comprises atopology of topology elements representing aspects of the project, andwherein the topology elements are selected from a palette of landscapeelements. The computer-implemented method, computer program product andsystem comprise linking each topology element to a respective one ormore solution artifacts from a plurality of solution artifacts for theproject. Additionally, the computer-implemented method, computer programproduct and system comprise validating, by operation of one or morecomputer processors, at least one of: (i) the plurality of solutionartifacts for the project; (ii) semantics of the information landscapebased on the topology of topology elements; and (iii) semantics of thelinking between each of the topology elements in the topology and theone or more solution artifacts.

Yet another embodiment of the invention provides a computer-implementedmethod for providing an information landscape for a project, wherein theinformation landscape comprises a topology of topology elementsrepresenting aspects of the project, and wherein the topology elementsare selected from a palette of landscape elements. The method includeslinking each topology element to a respective one or more solutionartifacts from a plurality of solution artifacts for the project.Additionally, the method includes linking each topology element to arespective one or more requirements from a plurality of requirements forthe project. The method also includes validating at least one topologyelement in the topology by operation of one or more computer processors,including determining an adequacy value for the one or more linkedsolution artifacts from the plurality of solution artifacts of theproject. The method further includes displaying the topology, includinggenerating a solution sketch based on the topology, wherein the solutionsketch comprises a graphical representation of the information landscapefor the project; and displaying the solution sketch based on a viewpointassociated with the topology.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited aspects are attained andcan be understood in detail, a more particular description ofembodiments of the invention, briefly summarized above, may be had byreference to the appended drawings.

It is to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 is a block diagram of components of a computer system configuredto run an information integration component, according to one embodimentof the invention.

FIGS. 2A-2B are block diagrams of exemplary embodiments of the computermemory of the computer system of FIG. 1.

FIG. 3 is a flow diagram illustrating a method of generating andvalidating a topology, according to one embodiment of the invention.

FIG. 4 is a flow diagram illustrating a method of generating andvalidating a topology, according to one embodiment of the invention.

FIG. 5 is a flow diagram illustrating a method of generating a paletteelement for use in a topology, according to one embodiment of theinvention.

FIG. 6 is a flow diagram illustrating a method of displaying a topology,according to one embodiment of the invention.

FIG. 7 is a flow diagram illustrating a method of displaying results ofa validation operation, according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Information integration projects are often very complex projectsinvolving multiple stakeholders with different perspectives anddifferent objectives. Large projects may also bring together a widerange of technical platforms, each with their own tools, capabilitiesand degrees of metadata management and reporting. As a result, thestakeholders will typically each have a fragmented view of the solutionlandscape. One embodiment of the invention provides an informationlandscape topology containing topology elements. Each of the topologyelements may be linked to one or more solution components. A validationcomponent may then validate the topology and the solution components. Inone embodiment, a displayable solution sketch may be generated based onthe topology. The solution sketch may be generated further based on aspecified viewpoint.

In the following, reference is made to embodiments of the invention.However, it should be understood that the invention is not limited tospecific described embodiments. Instead, any combination of thefollowing features and elements, whether related to differentembodiments or not, is contemplated to implement and practice theinvention. Furthermore, although embodiments of the invention mayachieve advantages over other possible solutions and/or over the priorart, whether or not a particular advantage is achieved by a givenembodiment is not limiting of the invention. Thus, the followingaspects, features, embodiments and advantages are merely illustrativeand are not considered elements or limitations of the appended claimsexcept where explicitly recited in a claim(s). Likewise, reference to“the invention” shall not be construed as a generalization of anyinventive subject matter disclosed herein and shall not be considered tobe an element or limitation of the appended claims except whereexplicitly recited in a claim(s).

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring now to FIG. 1, FIG. 1 is a block diagram of components of acomputer system configured to run an information integration component,according to one embodiment of the invention. As shown, FIG. 1 includesa computer system 100. The computer system 100 contains a computerprocessor 120, storage media 122, I/O devices 124 and memory 126.Computer processor 120 may be any processor capable of performing thefunctions described herein. I/O devices 124 may represent a variety ofinput and output devices, including keyboards, mice, visual displays,printers and so on. Furthermore, as will be understood by one ofordinary skill in the art, any computer system capable of performing thefunctions described herein may be used.

In the pictured embodiment, memory 126 contains an informationintegration component 128, a list of solution components 132 and anoperating system 134. Although memory 126 is shown as a single entity,memory 126 may include one or more memory devices having blocks ofmemory associated with physical addresses, such as random access memory(RAM), read only memory (ROM), flash memory or other types of volatileand/or non-volatile memory. The information integration component 128may contain an information landscape topology 130. The topology 130 mayinclude a representation of an information landscape or informationproject. Additionally, the information landscape topology 130 mayrepresent the information project from a particular viewpoint. Theoperating system 134 may be any operating system capable of performingthe functions described herein.

The list of solution components 132 may contain one or more solutioncomponents used in the information project. Generally, the solutioncomponents in the list of solution components 132 may include anycomponent used in an information project. In one embodiment, multipleseparate topologies 130 may share a single list of solution components132. In another embodiment, each topology 130 is associated with adedicated corresponding list of solution components 132.

In one embodiment, exemplary solution components include physicalmetadata structures, such as extract, transform and load (ETL) jobdesigns, deployed database schemas, and federated queries. Additionally,exemplary solution components may include model structures, such aslogical data models, dimensional models, physical data models, andmapping specifications. Furthermore, exemplary solution components mayinclude business definitions, such as requirements specifications,ontology elements, taxonomy elements or other business definitions.Exemplary solution components in the list of solution components 132 mayalso include operation structures, such as ETL job runs and ETL events.Of course, the above-listed embodiments of solution components aremerely for illustrative purposes, and one of ordinary skill in the artwill recognize that the solution components may represent other similarknown and unknown components.

The information integration component 128 may generally construct,maintain and validate an information landscape topology 130. In oneembodiment, the information landscape topology 130 contains a high-levelrepresentation of the information project. In addition, the topology 130may represent the information project in various ways and from a varietyof different viewpoints. For example, a network engineer using theinformation integration component 128 may view the topology 130 for theinformation project from a networking viewpoint, which may emphasizevarious networking devices and connections used in the informationproject. As another example, a sales executive using the informationintegration component 128 may view the topology 130 from a salesviewpoint, which may emphasize sales and customer information. In otherwords, different information in the topology may be shown and emphasizedin the topology, based on which viewpoint is used to view the topology130. As a result, multiple users, as well as multiple types of users(e.g., engineers, executives, etc.), may share a single topology model,but may still view the topology from a viewpoint that emphasizesinformation relevant to the user.

The information landscape topology 130 may also contain, for eachelement in the topology 130, one or more links to solution componentsfrom the list of solution components 132. For example, a “CustomerInformation” element in the topology 130 may map to a plurality ofsolution components from the list of solution components 132, such asdatabases storing customer information, database tables in the databasescontaining customer information, and web applications for updating thecustomer information in the database tables. By linking the topologyelements to one or more solution components, the topology elements arethus associated with dynamic values that may be updated as the projectevolves. Additionally, the information integration component 128 mayperform validation on the information landscape topology 130, the listof solution components 132, and on the various links from elements inthe topology 130 to one or more solution components. The validation mayensure not only the accuracy of these components and links, but also maydetermine whether certain business metrics can be met. The validation isdescribed in more detail in FIG. 3 and the related discussion.

FIGS. 2A-2B are block diagrams of exemplary embodiments of the computermemory of the computer system of FIG. 1. As shown, FIG. 2A represents afirst embodiment of a computer memory 126. The memory 126 includes aninformation integration component 128, a list of solution components132, an operating system 134, and a list of requirements 226. Theinformation integration component 128 further includes a topologycomponent 220, a linking component 222, a validation component 224 andan information landscape topology 130. The topology component 220 maygenerally generate and maintain the information landscape topology 130.

In one embodiment, for instance, a user may use the topology component220 to generate a new topology 130. The user may further use thetopology component 220 to generate new palette elements and add theseelements to the topology 130. As used herein, palette elements aregenerally landscape elements that may be added to one or more topologies130. For example, one exemplary palette element may be a “CustomerInformation” element, which may be added to a topology 130 representingan online shopping website. Furthermore, as defined herein, once apalette element is added to a topology, the instance of the element inthe topology is referred to as a topology element. Thus, as an example,adding a particular palette element to two separate topologies 130 willproduce two distinct topology elements: one represented by the instanceof the palette element in the first topology, and a second representedby the instance of the palette element in the second topology.

The information integration component 128 also contains a linkingcomponent 222. The linking component 222 may generally create andmaintain links between elements in a topology 130 and one or moresolution components from the list of solution components 132. Continuingthe above example, once the “Customer Information” palette element isadded to a topology 130, the element in the topology may be linked,using the linking component 222, with one or more solution componentsthat relate to customer information. For instance, the “CustomerInformation” element in the topology 130 may be linked to a databasestoring customer data, as well as a webpage used to create and modifydata in the database. In this example, both the database and the webpagemay be represented as solution components in the list of solutioncomponents 132. Furthermore, the linking component 222 may also linktopology elements with one or more requirements from the list ofrequirements 226. In one embodiment, multiple separate topologies 130may share a single list of requirements 226. In another embodiment, eachtopology 130 is associated with a dedicated corresponding list ofrequirements 226.

Additionally, in the pictured embodiment, the information integrationcomponent 120 contains a validation component 224. The validationcomponent 224 may generally be used to perform validation operations onother elements of the system. In one embodiment, the validationcomponent 224 may be used to validate the accuracy and existence ofsolutions in the list of solution components 132. In another embodiment,the validation component 224 may validate the information landscapetopology 130. Validation of the topology 130 may include validating notonly the elements of the topology 130, but also any links between thetopology elements and the solution components.

FIG. 2B is a block diagram of a second embodiment of the computer memoryof the computer system of FIG. 1. As shown, FIG. 2B shows an exemplarycomputer memory 126 containing an information integration component 128.The information integration component 128 contains a linking component222, a validation component 224 and a topology component 220. Thelinking component 222 further contains a requirement linking component230 and a solution tool linking component 232. The solution tool linkingcomponent 232 may link topology elements in the information landscapetopology 130 with one or more solution components in the list ofsolution components 132. The requirement linking component 230 may linktopology elements with one or more requirements from the list ofrequirements 226. For instance, one requirement in the list ofrequirements 226 may be that customer information must be saved for atleast one year after the customer completes a transaction. Thus,continuing with the above example, a user may use the requirementlinking component 230 to link the “Customer Information” topologyelement with the requirement that customer data be saved for at leastone year after the customer completes the transaction.

As shown, the topology component 220 further contains a solution sketch234, a solution tools component 236, a collection of palette elements242 and viewpoints 244. The topology component 220 may be used togenerate and manage the collection of palette elements 242. Continuingthe above example, a user may have used the topology component 220 togenerate the palette element of “Customer Information.” Once the elementis generated, the topology component 220 may add the element to thecollection of palette elements 242. The palette element 242 may then beadded to one or more topologies 130. For example, the “CustomerInformation” palette element may be added to two different topologies130, and each instance of the topology element may then be linked to adifferent set of both solution components 132 and requirements 226.

In one embodiment, the solution sketch 234 is a graphical representationof the information landscape topology 130. The solution sketch 234 maybe generated by the topology component 220. Additionally, the solutionsketch 234 may be displayed using one or more I/O devices 124 in thesystem 100. In one embodiment, the topology component 220 generatesmultiple solution sketches 234, with each solution sketch 234representing the topology 130 according to a different viewpoint 244.For example, a solution sketch 234 generated for display to a networkengineer (using a first viewpoint) may be different from a solutionsketch 234 generated for display to a sales executive (using a secondviewpoint). Thus, the two solution sketches 234 may be completelydifferent from one another because they are generated using differentviewpoints, even though both solution sketches 234 represent the sameinformation landscape topology 130.

In the pictured embodiment, the solution tools component 236 furthercontains a business tools component 238 and a technical tools component240. The business tools component 238 may generally be used to createand modify business components. For example, a user may use the businesstools component 238 to generate a new business requirement for aproject. Once the requirement is created, the business tools component238 may add the new requirement to the list of requirements 226. Thebusiness tools component 238 may also be used to create businessmetrics, which may be used in validation of the project performed by thevalidation component 224.

Additionally, the technical tools component 240 may be used to createand modify solution components. For example, a user may use thetechnical tools component 240 to generate a new solution component. Oncethe solution component is created, the technical tools component 240 mayadd the solution component to the list of solution components 132.Additionally, the technical tools component 240 may create and manageviewpoints 244. Furthermore, the technical tools component 240 may beused to create a new viewpoint 244 and associate the viewpoint 244 witha particular user. In one embodiment, the technical tools component 240may associate viewpoints 244 with a particular class of users. Forexample, the technical tools component 240 may generate a “NetAdmin”viewpoint, which may be used to generate a solution sketch 234 thatemphasizes networking devices and their connections. The technical toolscomponent 240 may then associate the viewpoint with user “John Smith.”Continuing this example, the technical tools component 240 may furtherassociate the viewpoint with the group of users “NetworkAdministrators,” which contains all the users involved in the projectthat are network administrators. As such, when John Smith (or any userthat is a network administrator) requests the topology component 220generate a solution sketch 234 for the topology 130, the generatedsolution sketch 234 will reflect the project with an emphasis onnetworking devices and connections.

FIG. 3 is a flow diagram illustrating a method of generating andvalidating a topology, according to one embodiment of the invention. Asshown, the method 300 begins at step 320, where the topology component220 generates a new palette element 242. For example, as discussedabove, a user may use the topology component 220 to generate the“Customer Information” palette element 242. The topology component 220may then add the palette element 242 to an information landscapetopology 130 (step 322). In one embodiment, the palette element 242 mayfurther be added to multiple different topologies 130 representingseparate projects. For example, the “Customer Information” paletteelement 242 may be added to a first topology 130 representing an onlineshopping website, and also added to a second topology 130 representing autility service.

Once the palette element 242 has been added to a topology 130, theinstance of the palette element in the topology 130 is then linked toone or more solution components 132 (step 324). In one embodiment, thelinking is performed using the solution tool linking component 232.Continuing the example, the two instances of the “Customer Information”palette element 242 in the two topologies 130 (i.e., the topology forthe online shopping website and the topology for the utility service)may be linked to completely separate requirements 226 and solutioncomponents 132. That is, because the online shopping website and theutility service will likely have different solution components (e.g.,databases, network devices, etc.) and different business requirements,the two instances of the “Customer Information” element 242 may belinked to entirely different structures within each of the respectivetopologies 130.

Once the topology element has been linked to one or more solutioncomponents, the topology element is then linked with one or morerequirements (step 326). In one embodiment, this linking is performedusing the requirement linking component 230. As noted above, in oneembodiment, a particular palette element 242 may be added to multipletopologies 130. Furthermore, in one embodiment, each instance of thepalette element 242 (i.e., the corresponding topology element in each ofthe different topologies 130) may be linked to different requirementsfrom the list of requirements 226. Furthermore, if each of the differenttopologies 130 uses a different list of requirements 226, the separateinstances of the palette element 242 may be linked not only withdifferent requirements, but different requirements from different listsof requirements 226.

As shown, the validation component 224 then performs a validationoperation (step 328). Generally, the validation component 224 mayvalidate different elements representing entities in the informationproject. In addition, the validation component 224 may notify a user ofthe results of the validation, including any problems or warnings thatwere detected. For example, in one embodiment, the validation component224 may validate an information landscape topology 130. As an example,the validation component 224 may perform syntactical validation, such asverifying the syntax of the topology 130. Additionally, exemplaryvalidation may include validating any links associated with the topologythat relate topology elements in the topology 130 to one or moresolution components 132 and requirements 226. Furthermore, thevalidation may include more advanced calculations, such as determining,for all paths and connections between topology elements in the topology130, which of these paths can be technically realized at the physicallevel. For example, a user may create a topology 130 showing a “CustomerInformation” element communicating directly with a “Store Inventory”element. Furthermore, in this example, the user may link the “CustomerInformation” topology element with a first database, and link the “StoreInventory” topology element with a second database. However, if the twodatabases are unable to directly communicate with each other (e.g., ifthey are on separate computer systems with no network path in between),the validation component 224 may detect this problem while performingthe validation. The validation component 224 may then report itsfindings to the user.

The validation component 224 may also validate the topology 130 todetermine the completeness of the business definition. In oneembodiment, the validation component 224 may analyze the topology 130 todetermine what assets (or percentage of assets) in the topology arelinked to adequate solution components 132 and requirement definitions226. For example, a “Customer Information” element in an exemplarytopology 130 may be linked to a solution component 132 representing awebpage for submitting customer data, and may additionally be linked toa requirement 226 specifying that customer information must be storedfor at least one year after the customer completes a transaction. Aspart of performing the validation, the validation component 224 maydetermine that, in this example, the “Customer Information” topologyelement is linked to inadequate solution components 132, because theelement is not linked with any solution components 132 capable ofsatisfying the requirement (i.e., the element is not linked with a“storage” component). Upon determining that the element is linked withinadequate solution components 132, the validation component 224 maynotify the user of its findings. In one embodiment, the validationcomponent 224 (or another component of the system 100) may also promptthe user with one or more suggested actions for remedying theinadequacy. The validation component 224 may prompt the user with a listof solution components from the list of solution components 132 that maybe linked to the “Customer Information” element in order to cure theinadequacy. Thus, in this example, the validation component 224 mayprompt the user with one or more available storage solution components.

Additionally, the validation component 224 may calculate, as part of thevalidation, one or more business metrics for the topology. For example,an exemplary information landscape topology 130 may express a means tosupport a business metric (such as Customer Profitability). In thisexample, the validation component 224 may determine, as part of thevalidation, to what degree these metrics may be technically realized,given the elements in the topology 130, their connections with oneanother, and their individual links to one or more solution components132 and requirements 226. Additionally, the validation component 224 maycalculate an estimated time indicating approximately when elements inthe topology (and their respective linked solution components 132 andrequirements 226) will be completely supported. For example, assume anexemplary topology 130 is created before all elements of the informationproject have been completed, and that the exemplary topology 130contains a “Customer Information” topology element linked to a websitesolution component and a database solution component. In this example,the website solution component may include a completion time of 6months, and the database solution component a completion time of 3months. Thus, in this example, the validation component 224 maydetermine that it will be 6 months until the “Customer Information”element is completely supported.

As a second example, the database solution component may include acompletion time of 3 months, and the website solution component mayinclude a completion time of 6 months after the completion of thedatabase solution component 132. In this example, the validationcomponent 224 may determine that it will be 9 months until the “CustomerInformation” element is completely supported. Of course, these examplesare for illustrative purposes only, and one of ordinary skill in the artwill recognize that other techniques for estimating and calculating atime until completion may be used instead. Additionally, the aboveexamples of exemplary validations are not meant to be limiting, butrather are intended for illustrative purposes. The validation component224 may of course perform other validations on these and other elementsof the project.

FIG. 4 is a flow diagram illustrating a method of generating andvalidating a topology, according to one embodiment of the invention. Asshown, the method 400 begins at step 420, where the topology component220 generates a new topology 130. For example, the topology component220 may generate the topology 130 in response to receiving a userrequest for a new topology 130. Once the topology has been generated,the topology component 220 receives a selection of a palette element 242(step 421). Continuing the above example, the user may choose a paletteelement 242 to add to the topology from a list of palette elements 242displayed using a user interface. Once the palette element selection isreceived, the topology component 220 determines whether the paletteelement already exists (step 422). For example, if, as in the aboveexample, the user selects the palette element 242 from a list ofelements displayed on a user interface, the topology component 220 maydetermine that the element already exists. However, if instead the userselected the element by using, for example, a “New Palette Element”button on the user interface, the topology component 220 may determinethat the palette element does not exist. In this case, the topologycomponent 220 generates a new palette element 242 (step 424). In oneembodiment, the new palette element 242 is generated based on inputreceived from the user. For example, a user may specify that thetopology component 220 should generate a new palette element named“Customer Information.”

Once the topology component 220 determines the selected palette element242 exists (step 422), or alternatively once the topology component 220generates the new palette element 242 (step 424), the topology component220 adds the palette element 242 to the newly generated topology 130(step 426). Upon adding the palette element 242 to the topology 130, thelinking component 222 links the topology element (i.e., the instance ofthe newly-added palette element 242 in the topology 130) with one ormore solution components from the list of solution components 132 (step428). In one embodiment, the linking is performed by the solution toollinking component 232. The linking component 222 may then link thetopology element with one or more requirements from the list ofrequirements 226 (step 429). In one embodiment, this is performed by therequirement linking component 230. Once the topology element is linkedwith one or more requirements, the validation component 224 validatesthe topology (step 430). Upon completing the validation, the method 400ends.

FIG. 5 is a flow diagram illustrating a method of generating a paletteelement for use in a topology, according to one embodiment of theinvention. As shown, the method 500 begins at step 518, where thetopology component 220 receives a selection of a palette element 242.The topology component 220 then determines whether the palette element242 currently exists (step 520). If the topology component 220determines the selected element 242 does not exist, the component 220generates a new palette element and adds the newly generated element tothe list of palette elements 242 (step 522).

Once the palette element is generated (step 522), or if the topologycomponent determines the palette element already exists (step 520), thetopology component 220 receives a selection of a sub-element to add tothe palette element (step 523). Generally, sub-element may refer to asub-section of the portion of an information project represented by apalette element. For example, a “Customer Information” palette elementmay further contain two sub-elements: a “Customer Information Interface”sub-element and a “Customer Information Storage” sub-element.Furthermore, when a palette element is added to a topology 130, anysub-elements contained in the palette element may be added to thetopology 130 as well. In addition, once added to the topology, thesesub-elements may be linked (e.g., by the linking component 222), similarto a topology element, to one or more solution components 132 and one ormore requirements 226.

Upon receiving the selection of the sub-element, the topology component220 determines whether the selected sub-element currently exists (step524). Thus, as a first example, a user may select an existingsub-element from a list of sub-elements displayed in a user interface.In the first example, the topology component 220 may determine that theselected sub-element already exists. As a second example, a user mayselect an “Add New Sub-Element” button in the user interface. In thesecond example, the topology component 220 may determine the selectedsub-element does not exist, and proceed to generate the new sub-element(step 526). The topology component 220 may generate the new sub-elementbased on input received from the user.

Once the topology component 220 determines the sub-element exists (step524), or once the topology component 220 generates the new sub-element(step 526), the topology component 220 adds the new sub-element to thepalette element (step 528). As an example, a user may specify a new“Customer Information” palette element, and further specify a “CustomerInformation Storage” sub-element. The topology component 220 may createboth the palette element and the sub-element, and then add thenewly-created sub-element to the palette element. Once the sub-elementis added to the palette element, the topology component 220 determinesif there are more sub-elements to add to the palette element (step 530).In one embodiment, this determination is made based on a responsereceived from the user. For instance, the topology component 220 maysimply query the user and ask whether the user wishes to add moresub-elements to the palette element. In this example, the topologycomponent 220 may then make the determination of step 530 based on aresponse from the user.

In any event, if the topology component 220 determines there are moresub-elements to add to the palette element, the loop begins again atstep 523, where the topology component 220 receives a selection ofanother sub-element. If, instead, the topology component 220 determinesthere are no more sub-elements to add, the validation component 224proceeds to validate the palette element and any included sub-elements.Once the validation is complete, the method 500 ends.

FIG. 6 is a flow diagram illustrating a method of displaying a topology,according to one embodiment of the invention. As shown, the method 600begins at step 620, where the topology component 220 receives aselection of a topology 130 to display. For example, an exemplaryinformation integration component 128 may contain multiple informationlandscape topologies: one for an online shopping website, and a secondfor a utility service. In this example, a user may indicate (e.g.,through a select operation performed using a user interface) that hewishes to view the topology for the online shopping website.

Once the topology component 220 receives the selection of the topology,the component 220 identifies a viewpoint 244 for displaying the topology130 (step 622). As explained above, a single topology 130 may berepresented in multiple different ways, based on the viewpoint 244 fromwhich the topology is displayed. Continuing the above example, thetopology 130 for the online shopping website may be associated with twoviewpoints: one viewpoint for network engineers, and a second viewpointfor sales executives. If a solution sketch 234 is created for thetopology 130 using the viewpoint for sales executives, the solutionsketch 234 may simply show a high-level representation of all thetopology elements in the topology. Conversely, if the solution sketch234 is created using the viewpoint for network engineers, the solutionsketch 234 may include additional details about the networkingconnections and devices used in the information project. Thus, twosolution sketches 234 created for the same topology 130 may differ,depending on the viewpoints 244 used in creating each of the solutionsketches 234.

The topology component 220 may identify a viewpoint 244 to use indisplaying the topology 130 based on a user selection of a viewpoint244. Thus, in one embodiment, the user may simply select a viewpoint 244(e.g., from a list of viewpoints displayed in a user interface) for usein generating a solution sketch 234 for the topology 130. In anotherembodiment, the viewpoint 244 may be identified based on the credentialsof the user. For example, if a user belongs to a networking user group,the topology component 220 may determine that the viewpoint for networkengineers should be used. In yet another embodiment, users may specify adefault viewpoint to use in viewing topologies in a user profile. Forexample, a particular user may specify that he wishes to view topologiesby default using the sales executive viewpoint. Thus, in thisembodiment, even if the particular user is a member of the networkinguser group, the sales executive viewpoint will be used when the userrequests to view a topology.

Once the viewpoint is identified, the topology component 220 generates asolution sketch 234 for the topology 130 using the identified viewpoint244, and displays the generated solution sketch 234 (step 624). In oneembodiment, the topology component 220 may also store the solutionsketch 234 as an image file on storage media 122. The generation andstorage of the image file may be, for example, in response to a userrequest. For instance, once the solution sketch 234 is displayed, theuser may request an image file be generated (e.g., by clicking a “Saveas Image . . . ” button in the user interface). In another embodiment,the topology component 220 may generate an image file representing thesolution sketch 234 in lieu of displaying the solution sketch 234. Oncethe solution sketch 234 is displayed, the method 600 ends.

FIG. 7 is a flow diagram illustrating a method of displaying results ofa validation operation, according to one embodiment of the invention. Asshown, the method 700 begins at step 720, where the topology component220 displays a solution sketch 234 generated for a topology 130. In oneembodiment, the solution sketch 234 may be generated and displayed usingmethod 600. Once the solution sketch 234 representing the topology 130is displayed, the validation component 224 receives a validation request(step 722). For example, a user interface used for displaying thesolution sketch may include a “Validate Topology” button which, ifpressed, submits a validation request.

Upon receiving the validation request, the validation component 224validates the topology (step 724). The validation may be any validationoperation described herein, including, but not limited to, syntaxvalidation, adequacy of solution components validation, physicalpossibility validation and business metric validation. Once thevalidation is complete, the validation component 224 displays theresults of the validation (step 726). As an example, if the validationcomponent 224 determines (at step 724) that a “Customer Information”topology element is linked to inadequate solution components because thetopology element is not linked to a storage solution component (e.g., adatabase), the validation component 224 may alert the user to thisinadequacy. Additionally, the validation component 224 may suggestactions that the user may take to remedy the inadequacy. Continuing theabove example, the validation component 224 may suggest that the userlink the “Customer Information” topology element with one or morestorage solution components. In one embodiment, the validation component224 may further present the user with a list of storage solutioncomponents from the list of solution components 132. The user may thenselect one of the storage solution components, and in response to theselection, the linking component 222 may link the “Customer Information”topology element with the selected storage solution component. Thevalidation component 224 may then perform a second validation operationon the topology, and notify the user that the inadequacy has beenremedied. Once the results of the validation are displayed, the method700 ends.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

What is claimed is:
 1. A computer program product to provide aninformation landscape for topology modeling, linking, and validation foran information integration project, the information landscape comprisinga topology of topology elements representing aspects of the informationintegration project, the computer program product comprising: acomputer-readable storage medium having computer-readable program codeof an information integration program embodied therewith, thecomputer-readable program code executable by one or more computerprocessors to perform an operation comprising: generating the topologybased on a palette of landscape elements; linking each topology elementto a respective one or more solution artifacts from a plurality ofsolution artifacts for the information integration project, wherein theplurality of solution artifacts includes at least one of a database, alogical data model for a database, and a database schema; determining adegree to which one or more business metrics are realizable, based on:(i) the plurality of solution artifacts for the information integrationproject; (ii) the information landscape; and (iii) the linking betweeneach of the topology elements in the topology and the respective one ormore solution artifacts; upon receiving a request from a user togenerate a solution sketch for the information landscape, determining aclass of users to which the user is assigned, based on an electronicuser identifier corresponding to the user; determining a viewpointhaving a predefined association with the class of users to which theuser is assigned; selecting only a portion of the plurality of solutionartifacts to depict, based on the viewpoint having a predefinedassociation with the class of users to which the user is assigned;automatically generating the solution sketch for the user, the solutionsketch comprising a graphical representation of the informationlandscape, wherein the solution sketch includes depictions of solutionartifacts for the selected portion of the plurality of solutionartifacts, wherein the solution sketch is generated based on: (i) thelinking of the topology elements to the solution artifacts, and (ii) theviewpoint having the predefined association with the class of users towhich the user is assigned; and outputting the solution sketch fordisplay to the user.
 2. The computer program product of claim 1, whereinthe operation further comprises: providing an information integrationprogram comprising a plurality of components including a topologycomponent, a linking component, and a validation component; wherein thetopology is generated by the topology component; wherein each topologyelement is linked to the respective one or more solution artifacts, bythe linking component; and wherein the degree to which one or morebusiness metrics are realizable is determined by the validationcomponent.
 3. The computer program product of claim 2, wherein a degreeto which the one or more business metrics are realizable comprises anaffirmative degree to which the one or more business metrics aretechnically realizable, wherein the linking component includes arequirement linking subcomponent and a solution tool linkingsubcomponent, wherein the requirement linking subcomponent linkstopology elements with one or more requirements from a plurality ofrequirements of the information integration project, wherein thesolution tool linking subcomponent links the topology elements with oneor more solution components; wherein the topology component includes abusiness tools subcomponent and a technical tools subcomponent, whereinthe business tools subcomponent creates and modifies business componentsand business metrics used in validating the information integrationproject, wherein the technical tools subcomponent creates and modifiessolution components and viewpoints; wherein the validation componentvalidates each of: (i) the plurality of solution artifacts for theinformation integration project; (ii) semantics of the informationlandscape based on the topology of topology elements; and (iii)semantics of the linking between each of the topology elements in thetopology and the respective one or more solution artifacts.
 4. Thecomputer program product of claim 3, wherein the operation furthercomprises: prior to determining the degree to which the one or morebusiness metrics are realizable, generating the one or more businessmetrics by the validation component based on: (i) the plurality ofsolution artifacts for the information integration project; (ii) theinformation landscape; and (iii) the linking between each of thetopology elements in the topology and the respective one or moresolution artifacts; and linking each topology element to a respectiveone or more requirements from the plurality of requirements for theinformation integration project; wherein the one or more businessmetrics are generable based on each aspect selected from: (i) thetopology of topology elements; (ii) the plurality of solution artifacts;and (iii) the linking between one or more topology elements in thetopology and the respective one or more solution artifacts.
 5. Thecomputer program product of claim 4, wherein the topology elements areselected from the palette of landscape elements, wherein a firstlandscape element of the palette of landscape elements contains one ormore sub-elements; wherein the operation further comprises: determining,for at least one topology element in the topology, an adequacy value forthe one or more linked solution artifacts from the plurality of solutionartifacts of the information integration project; and determining apossibility of one or more paths between topology elements in thetopology, based on the respective linked one or solution components foreach of the topology elements; wherein the plurality of solutionartifacts includes each of: (i) a physical metadata structure; (ii) amodel structure; (iii) a business definition; (iv) an operationstructure; and (v) a web resource.
 6. The computer program product ofclaim 5, wherein the physical metadata structure comprises each of: (i)an extract, transform and load (ETL) job design; (ii) a deployeddatabase schema; and (iii) a federated query.
 7. The computer programproduct of claim 6, wherein the model structure comprises each of: (i) alogical data model; (ii) a dimensional model; (iii) a physical datamodel; and (iv) a mapping specification.
 8. The computer program productof claim 7, wherein the one or more business metrics comprise a customerprofitability metric, wherein the business definition comprises each of:(i) a requirements specification; (ii) an ontology element; and (iii) ataxonomy element; wherein the operation structure comprises each of: (i)an ETL job execution; and (ii) an ETL event; wherein thecomputer-readable program code is executable to generate a respectivesolution sketch from a respective information landscape for eachinformation integration project type selected from: (i) a data warehouseproject; (ii) a data integration project; (iii) a data quality project;(iv) a business intelligence project; and (v) a master data managementproject.
 9. The computer program product of claim 1, wherein theoperation further comprises: linking each topology element to arespective one or more requirements from a plurality of requirements forthe information integration project.
 10. The computer program product ofclaim 1, wherein the operation further comprises: calculating the one ormore business metrics, based on at least one of the following: (i) thetopology of topology elements; (ii) the plurality of solution artifacts;and (iii) the linking between one or more topology elements in thetopology and the respective one or more solution artifacts.
 11. Thecomputer program product of claim 1, wherein the topology elements areselected from the palette of landscape elements, wherein a firstlandscape element of the palette of landscape elements contains one ormore sub-elements.
 12. The computer program product claim 1, wherein theoperation further comprises: determining, for at least one topologyelement in the topology, an adequacy value for the one or more linkedsolution artifacts from the plurality of solution artifacts of theinformation integration project.
 13. The computer program product ofclaim 1, wherein the operation further comprises: determining apossibility of one or more paths between topology elements in thetopology, based on the respective linked one or solution components foreach of the topology elements.
 14. A system to provide an informationlandscape for topology modeling, linking, and validation for aninformation integration project, the information landscape comprising atopology of topology elements representing aspects of the informationintegration project, the system comprising: a computer processor; and amemory containing an information integration program executable toperform an operation comprising: generating the topology based on apalette of landscape elements; linking each topology element to arespective one or more solution artifacts from a plurality of solutionartifacts for the information integration project, wherein the pluralityof solution artifacts includes at least one of a database, a logicaldata model for a database, and a database schema; determining a degreeto which one or more business metrics are realizable, based on: (i) theplurality of solution artifacts for the information integration project;(ii) the information landscape; and (iii) the linking between each ofthe topology elements in the topology and the respective one or moresolution artifacts; upon receiving a request from a user to generate asolution sketch for the information landscape, determining a class ofusers to which the user is assigned, based on an electronic useridentifier corresponding to the user; determining a viewpoint having apredefined association with the class of users to which the user isassigned; selecting only a portion of the plurality of solutionartifacts to depict, based on the viewpoint having a predefinedassociation with the class of users to which the user is assigned,wherein at least one of the plurality of solution artifacts is notselected; automatically generating the solution sketch for the user, thesolution sketch comprising a graphical representation of the informationlandscape, wherein the solution sketch includes depictions of solutionartifacts for the selected portion of the plurality of solutionartifacts, wherein the solution sketch is generated based on: (i) thelinking of the topology elements to the solution artifacts, and (ii) theviewpoint having the predefined association with the class of users towhich the user is assigned; and outputting the solution sketch fordisplay to the user.
 15. The system of claim 14, wherein the informationintegration program is configured to construct, maintain, and validatethe information landscape, wherein the operation further comprises:linking each topology element to a respective one or more requirementsfrom a plurality of requirements for the information integrationproject.
 16. The system of claim 14, wherein the operation furthercomprises: calculating one or more business metrics, based on at leastone of the following: (i) the topology of topology elements; (ii) theplurality of solution artifacts; and (iii) the linking between one ormore topology elements in the topology and the respective one or moresolution artifacts.
 17. The system of claim 14, wherein the topologyelements are selected from a palette of landscape elements, wherein afirst landscape element of the palette of landscape elements containsone or more sub-elements.
 18. The system of claim 14, wherein theoperation further comprises: determining, for at least one topologyelement in the topology, an adequacy value for the one or more linkedsolution artifacts from the plurality of solution artifacts of theinformation integration project.
 19. The system of claim 14, wherein theoperation further comprises: determining a possibility of one or morepaths between topology elements in the topology, based on the respectivelinked one or solution components for each of the topology elements. 20.The system of claim 14, wherein the degree to which the one or morebusiness metrics are realizable comprises an affirmative degree to whichthe one or more business metrics are technically realizable, wherein theone or more business metrics comprise a customer profitability metric.